Skip to content

test: refresh MiniMax model fixtures to M3#18

Open
octo-patch wants to merge 1 commit into
jmuncor:mainfrom
octo-patch:feature/upgrade-minimax-m3
Open

test: refresh MiniMax model fixtures to M3#18
octo-patch wants to merge 1 commit into
jmuncor:mainfrom
octo-patch:feature/upgrade-minimax-m3

Conversation

@octo-patch
Copy link
Copy Markdown

Summary

Refresh MiniMax model identifiers in test fixtures so the test suite reflects the current flagship model (MiniMax-M3).

Changes

  • Replace deprecated MiniMax-M2.5 references in tests/test_proxy.py and tests/test_integration.py with MiniMax-M3
  • Retain existing MiniMax-M2.7 fixtures to keep coverage for an alternate model identifier

Why

MiniMax-M3 is the new flagship model (512K context window, 128K max output, image input). Using it as the default sample body keeps the tests aligned with current usage patterns and lightly documents which model the proxy is being exercised against.

The proxy itself is model-agnostic — it forwards whatever model the caller sends in the request body — so this is a fixtures-only change with no behavior impact.

Testing

  • Full test suite passes locally (pytest tests/, 38 passed)

Replace deprecated MiniMax-M2.5 references in test fixtures with the
new flagship MiniMax-M3 model. Existing MiniMax-M2.7 fixtures are
retained to keep alternate-model coverage.

The proxy itself is model-agnostic (it forwards whatever model the
caller sends), so this change only refreshes sample request bodies
used in unit and integration tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant